Left a couple of comments about strings and the regex used to determine the feature's appropriateness.

HI @RitaDee - instead of creating an entirely new operation, let's instead augment the existing cycle highway tags operation to do both things. I apologize for not making this requirement clearer in my original issue writeup.

We'll need you to take the following actions:

1. Move the existing cycle crosswalk tag functionality into the main cycle_highway_tag.js file.
2. Ensure that it works in both cases: highways get their tags cycled correctly, AND crosswalks get their tags cycled correctly.
3. Remove the new cycle_crosswalk_tag: core.yaml entry and subentries for title, key, description, but keep the new annotation and put it under the cycle_highway_tag entry.

I hope that makes sense!

Needs refactoring! The highway logic and crossing logic should be kept separate, depending on what the user has selected, we should conditionally do one thing (cycle a crossing's tags) or the other (cycle a highway's tags).

Left a couple comments directly on the cycle_highway_tags source!